Skip to content

feat(ui): reliability foundation — error boundary, health banner, Vercel fix#18

Merged
askmy-stack merged 4 commits into
mainfrom
feat/ui-reliability-foundation
Jun 25, 2026
Merged

feat(ui): reliability foundation — error boundary, health banner, Vercel fix#18
askmy-stack merged 4 commits into
mainfrom
feat/ui-reliability-foundation

Conversation

@askmy-stack

@askmy-stack askmy-stack commented Jun 25, 2026

Copy link
Copy Markdown
Owner

Summary

  • Add React ErrorBoundary with StateView fallback and retry
  • Poll /health for global API status in the topbar and degraded banner
  • Exclude backend from Vercel builds via .vercelignore and root middleware.ts
  • Toast feedback on Connection save/clear with unified customer error copy

Test plan

  • npm run build passes
  • Error in a view shows recovery UI (manual)
  • Topbar health dot reflects API status when backend is down
  • Vercel preview deploy stays frontend-only

… fix.

Wrap the dashboard in an ErrorBoundary with recovery UI, poll /health for a
global status banner, and keep Vercel builds frontend-only via .vercelignore.
Connection save/clear now surfaces toast feedback with unified error copy.

Co-authored-by: Cursor <cursoragent@cursor.com>
…bundle.

Vercel was detecting pyproject.toml after the Vite build and packaging ~5.4 GB
of Python deps. Upload only frontend/ plus root deploy config so the bundle
stays under the 500 MB ephemeral storage limit.

Co-authored-by: Cursor <cursoragent@cursor.com>
Prepares Plan A API hosting alongside reliability foundation; full runbook
lands in PR #24 (DEPLOY-FREE.md).

Co-authored-by: Cursor <cursoragent@cursor.com>
PR #18 imported icons, onboarding context, and routing from later
stacked PRs, breaking TypeScript CI. Restore local onboarding state and
remove forward references so the reliability foundation builds alone.

Co-authored-by: Cursor <cursoragent@cursor.com>
Repository owner deleted a comment from vercel Bot Jun 25, 2026
@askmy-stack askmy-stack merged commit 06710ba into main Jun 25, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant